Blog post: List of principles when interacting with Open Source communities#179
Draft
Blog post: List of principles when interacting with Open Source communities#179
Conversation
sjn
changed the title
Contributor
Author
|
I'm thinking about good ways to introduce context to this topic. |
…' into sjn-principles-post
Contributor
You can turn it into a draft, which also prevents accidental merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This article is still a WIP.
The goal here is to enumerate some of the base (high-level) assumptions that needs to be in place for making sensible and constructive decisions around securing open source ecosystems like CPAN and Perl's.
Audience: Management-level; Market authorities; Secure software development guidance authors; etc.
Note: copied in from sjn-principles-post-2025-05 branch